Installing AutoVue Client/Server

Installing AutoVue Client/Server includes installing the AutoVue Client/Server software on a Java application server and installing the components that integrate AutoVue Client/Server with Meridian Explorer on the Explorer web server and on the Java application server (if separate). The AutoVue Client/Server software and documentation are available on the BlueCielo FTP server. Installation also includes configuring Explorer to connect to those components when a document should be viewed.

Notes

• If AutoCAD drawings will be viewed that use custom font (.shx) files, place copies of the font files in the following location after installation:

  C:\Oracle\AutoVue\bin\fonts

• BlueCielo product licenses include the use of AutoVue Client/Server for viewing 2D documents. Viewing 3D documents requires the installation of optional licenses (M--AV3) that are available at additional cost.
• When the Meridian Explorer server is upgraded to a new release, also upgrade the AutoVue server at the same time. The AutoVue server software must be the same version as the JVue applet that is included in the Meridian Explorer release.
• If Meridian Enterprise and Meridian Explorer are used together in the same environment, they can share the same AutoVue deployment:
  • AutoVue Desktop – The newer version of AutoVue Desktop that is installed by either application's installation package can be used with both products. A newer installed version of AutoVue will not be overwritten by installing the other product that includes an older version.
  • AutoVue Client/Server – The version of AutoVue Client/Server that is supported by the Meridian Enterprise version should be used by both Meridian Enterprise and Meridian Explorer. The integration components for Meridian Enterprise are installed only by the Meridian Enterprise installation package and are specific to a particular AutoVue Client/Server version. The .jar files that are installed by Meridian Explorer (by default, in C:\inetpub\wwwroot\<WebSite>\Jar\Res) should be replaced by the versions that are installed by Meridian Enterprise (by default, in C:\inetpub\wwwroot\AMM\Res).

The AutoVue Client/Server software includes a copy of the open source Java application server software Jetty. This is convenient if you will be deploying AutoVue Client/Server and do not have an existing Java application server on which to host AutoVue. It is also useful if you want a lightweight Java application server for desktop deployment. For convenience, the AutoVue Client/Server installation packages install Jetty support by default. These instructions can be used to install AutoVue Client/Server as a desktop deployment. In that case, the references to different computers apply to the same computer.

Before you begin

• Microsoft .NET Framework 3.5 SP1 is required on the web server where the BlueCielo web service is installed in this task.
• Meridian Explorer can use an existing AutoVue server that has already been configured to work with Meridian Enterprise as described in the BlueCielo Meridian Enterprise Administratorʹs Guide. Alternatively, another instance can be installed on a different server.

To install AutoVue Client/Server:

1. Ensure that the server and client computers meet the hardware and software requirements described in the Oracle AutoVue Client/Server Deployment Installation and Configuration Guide and in the BlueCielo Meridian Explorer Administrator’s Guide.

2. If an existing installation of AutoVue Client/Server will not be used, perform this step. Otherwise, skip to the next step.

   On the computer that will be the AutoVue server, install the AutoVue 2D or AutoVue 3D server software using its respective Oracle setup program. Use the instructions for non-integrated installation in the Oracle AutoVue Client/Server Deployment Installation and Configuration Guide. The following table lists the installation option responses that are adequate for integration with Meridian Explorer.

   Oracle AutoVue Client/Server installation options

   Option	Setting
   Specify Installation Directory	Accept the default (C:\Oracle\AutoVue)
   Select Install Set	Standard
   Select Shortcut Folder	Accept the default (Oracle AutoVue)
   Specify hostname or IP address for the AutoVue Server	Accept the default
   AutoVue Server Authentication	Configure Later
   Enabling SSL Communication	If you do not want to use the SSL protocol, select Configure Later. If you do want to use SSL: Select Configure SSL with a CA certificate and click Next. The Select the CA certificate file page appears. Select a valid CA certificate and click Next. The Select the Identity JKS Keystore file page appears. Click Next. A default file will be created as: C:\oracle\autovue\bin\AutoVueIdentity.jks The Specify the Identity JKS Keystore password page appears. Type a password and click Next. The password will be stored in the file: C:\oracle\autovue\bin\jetty\etc\jetty-ssl.xml Perform the rest of the steps described in NEW Configuring viewing with SSL.

   Tip    These settings configure the AutoVue server as a stand-alone application that can be used outside of Explorer by opening the page at http://<ServerName>/jVue/jVue.html.

3. On the same computer, run the Meridian Enterprise setup program that contains the same AutoVue Client/Server version as the installed version of AutoVue and install the AutoVue Client/Server Integration component. This will add the BlueCielo Connector to AutoVue and install a BlueCielo web service in the IIS default website. If the Meridian Enterprise web server is a separate computer, run the setup program there also.

4. On the Meridian Enterprise web server, test the web service by opening it in a browser with the following URL.

   http://<ServerName>/BCWebService/BCWebService.BluePrintService.svc

   A page titled appears if installation is correct to this point.

5. On the AutoVue server, open the file StartServers.bat in any text editor and verify that the paths are correct for your installation. By default, it is located in C:\Oracle\AutoVue\bin.

6. NEW  By default, the Jetty application server, the AutoVue servlet, and the BlueCielo connector servlet will be started automatically. If this fails due to system configuration or security issues, the server can be started manually by running StartServers.bat. Two Command Prompt windows and the AutoVue Server console window appear. The windows must stay open but can be minimized. For more information about starting the servers automatically, see Starting the servers automatically.

7. Test AutoVue Client/Server by opening a document in the client application. The AutoVue applet downloads from the web server and opens the selected document.

   Notes    To prevent the Java authentication dialog from appearing at the beginning of each viewing session, you may need to configure one or more of the following settings:

   • Add the fully qualified name of the AutoVue server to the Local intranet zone in the Internet Explorer security options on the client computers but do not add it to the Trusted sites list.
   • Add the account name that is used for the application pool under which the web application is run (for example, Web Access or Meridian Explorer) to the Act as part of the operating system policy using the Local Group Policy Editor.
   • Define an authentication level for Network security: LAN Manager authentication level using the Local Group Policy Editor. The setting cannot be Not Defined.
   • On Windows Server 2003 and Windows XP computers, the account under which the BCConnectorService logs on should be changed from Local System to an account that has access to the website.

For more information about configuring and administering AutoVue Client/Server, see:

• Oracle AutoVue Client/Server Deployment Installation and Configuration Guide
• Oracle AutoVue Desktop Deployment Installation and Configuration Guide